System and method for vehicle position and velocity estimation based on camera and lidar data

ABSTRACT

A vehicle position and velocity estimation system based on camera and LIDAR data is disclosed. An embodiment includes: receiving input object data from a subsystem of a vehicle, the input object data including image data from an image generating device and distance data from a distance measuring device, the distance measuring device comprising one or more LIDAR sensors; determining a first position of a proximate object near the vehicle from the image data; determining a second position of the proximate object from the distance data; correlating the first position and the second position by matching the first position of the proximate object detected in the image data with the second position of the same proximate object detected in the distance data; determining a three-dimensional (3D) position of the proximate object using the correlated first and second positions; and using the 3D position of the proximate object to navigate the vehicle.

PRIORITY PATENT APPLICATIONS

This patent application is a continuation patent application drawing priority from U.S. non-provisional patent application Ser. No. 16/752,637; filed Jan. 25, 2020; which is a continuation patent application drawing priority from U.S. non-provisional patent application Ser. No. 15/496,113; filed Apr. 25, 2017, now U.S. Pat. No. 10,552,691. This present non-provisional patent application draws priority from the referenced patent application. The entire disclosure of the referenced patent application is considered part of the disclosure of the present application and is hereby incorporated by reference herein in its entirety.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the U.S. Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever. The following notice applies to the disclosure herein and to the drawings that form a part of this document: Copyright 2016-2022, TuSimple, Inc., All Rights Reserved.

TECHNICAL FIELD

This patent document pertains generally to tools (systems, apparatuses, methodologies, computer program products, etc.) for trajectory planning, vehicle control systems, and autonomous driving systems, and more particularly, but not by way of limitation, to a system and method for vehicle position and velocity estimation based on camera and LIDAR (Light Imaging, Detection, And Ranging) data.

BACKGROUND

An autonomous vehicle is often configured to follow a trajectory based on a computed driving path. However, when variables such as obstacles are present on the driving path, the autonomous vehicle must perform control operations so that the vehicle may be safely driven by changing the driving path to avoid the obstacles. In many cases, data from cameras can be used to detect obstacles in the path. In other cases, LIDAR data can be used. LIDAR (also called Lidar, LiDAR, and LADAR) is a surveying method that measures distance to a target by illuminating that target with a pulsed laser light and measuring the reflected pulses with a sensor. Differences in laser return times and wavelengths can then be used to make digital representations of the target. The term LIDAR is sometimes considered an acronym of Light Detection And Ranging (sometimes Light Imaging, Detection, And Ranging). However, the independent analysis of image data from the camera or distance data from the LIDAR can produce inaccurate results and lead to dangerous situations for the autonomous vehicle.

SUMMARY

A system and method for vehicle position and velocity estimation based on camera and LIDAR data are disclosed herein. Specifically, the present disclosure relates to a system and method to detect and estimate the position of proximate vehicles in the vicinity of an autonomous vehicle, as well as estimating the velocity of the proximate vehicle relative to the autonomous vehicle. The system includes two major phases: 1) a data collection phase, and 2) an inference and tracking phase. In the data collection phase, a vehicle, on which is mounted one or more cameras (or other image generating devices) and one or more LIDAR sensors (or other distance measuring devices), collects multiple frames of images from a video stream generated by the camera(s) and multiple LIDAR point clouds, respectively, at a pre-determined time interval (e.g., 50 milliseconds). In the inference and tracking phase, implemented in an example embodiment by an inference and tracking module, two-dimensional (2D) positions of proximate vehicles and other objects can be detected using the image data from the camera(s). Additionally, distance data, corresponding to the objects detected from the image data, can be obtained from the LIDAR point clouds. Using both the 2D positions of proximate vehicles determined from the image data and the estimates of relative distance of the proximate vehicles using the LIDAR distance data, the inference and tracking module can determine the precise relative three dimensional (3D) position of proximate vehicles relative to the autonomous vehicle. As multiple estimates of position are determined over time at a pre-determined sample rate or cycle time (e.g., 50 milliseconds), the inference and tracking module may also determine the estimated relative velocity of each proximate vehicle relative to the autonomous vehicle. With the assistance of a 3D tracking process, the system of an example embodiment can determine the relative 3D positions and velocities of proximate vehicles using camera image data and LIDAR distance data, even when intermittent, errant, or unstable camera image data or LIDAR data is received.

BRIEF DESCRIPTION OF THE DRAWINGS

The various embodiments are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings in which:

FIG. 1 illustrates a block diagram of an example ecosystem in which a vehicle position and velocity estimation module of an example embodiment can be implemented;

FIGS. 2 and 3 illustrate the components of the vehicle position and velocity estimation system of an example embodiment;

FIG. 4 is a process flow diagram illustrating an example embodiment of a method for vehicle position and velocity estimation based on camera and LIDAR data; and

FIG. 5 shows a diagrammatic representation of machine in the example form of a computer system within which a set of instructions when executed may cause the machine to perform any one or more of the methodologies discussed herein.

DETAILED DESCRIPTION

In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the various embodiments. It will be evident, however, to one of ordinary skill in the art that the various embodiments may be practiced without these specific details.

As described in various example embodiments, a system and method for vehicle position and velocity estimation based on camera and LIDAR data are described herein. An example embodiment disclosed herein can be used in the context of an in-vehicle control system 150 in a vehicle ecosystem 101. In one example embodiment, an in-vehicle control system 150 with a vehicle position and velocity estimation module 200 resident in a vehicle 105 can be configured like the architecture and ecosystem 101 illustrated in FIG. 1 . However, it will be apparent to those of ordinary skill in the art that the vehicle position and velocity estimation module 200 described and claimed herein can be implemented, configured, and used in a variety of other applications and systems as well.

Referring now to FIG. 1 , a block diagram illustrates an example ecosystem 101 in which an in-vehicle control system 150 and a vehicle position and velocity estimation module 200 of an example embodiment can be implemented. These components are described in more detail below. Ecosystem 101 includes a variety of systems and components that can generate and/or deliver one or more sources of information/data and related services to the in-vehicle control system 150 and the vehicle position and velocity estimation module 200, which can be installed in the vehicle 105. For example, a camera installed in the vehicle 105, as one of the devices of vehicle subsystems 140, can generate image and timing data that can be received by the in-vehicle control system 150. The in-vehicle control system 150 and an image processing module executing therein can receive this image and timing data input. The image processing module can extract object data from the image and timing data to identify objects in the proximity of the vehicle 105. Additionally, a LIDAR sensor installed in the vehicle 105, as another one of the devices of vehicle subsystems 140, can generate distance data as point clouds that can be received by the in-vehicle control system 150. The in-vehicle control system 150 and a LIDAR data processing module executing therein can receive this distance data and point cloud input. The LIDAR data processing module can generate distance data relative to objects detected in the proximity of the vehicle 105. As described in more detail below, the vehicle position and velocity estimation module 200 can process the object image data and object distance data of detected objects to generate a position and velocity for each proximate object near the autonomous vehicle 105. The proximate object position and velocity data can be used by an autonomous vehicle control subsystem, as another one of the subsystems of vehicle subsystems 140, to maintain the vehicle 105 on a path that does not intersect with the paths of the proximate objects. The autonomous vehicle control subsystem, for example, can use the proximate object position and velocity data to safely and efficiently navigate the vehicle 105 through a real world driving environment while avoiding obstacles and safely controlling the vehicle.

In an example embodiment as described herein, the in-vehicle control system 150 can be in data communication with a plurality of vehicle subsystems 140, all of which can be resident in a user's vehicle 105. A vehicle subsystem interface 141 is provided to facilitate data communication between the in-vehicle control system 150 and the plurality of vehicle subsystems 140. The in-vehicle control system 150 can be configured to include a data processor 171 to execute the vehicle position and velocity estimation module 200 for processing object data received from one or more of the vehicle subsystems 140. The data processor 171 can be combined with a data storage device 172 as part of a computing system 170 in the in-vehicle control system 150. The data storage device 172 can be used to store data, processing parameters, and data processing instructions. A processing module interface 165 can be provided to facilitate data communications between the data processor 171 and the vehicle position and velocity estimation module 200. In various example embodiments, a plurality of processing modules, configured similarly to vehicle position and velocity estimation module 200, can be provided for execution by data processor 171. As shown by the dashed lines in FIG. 1 , the vehicle position and velocity estimation module 200 can be integrated into the in-vehicle control system 150, optionally downloaded to the in-vehicle control system 150, or deployed separately from the in-vehicle control system 150.

The in-vehicle control system 150 can be configured to receive or transmit data from/to a wide-area network 120 and network resources 122 connected thereto. An in-vehicle web-enabled device 130 and/or a user mobile device 132 can be used to communicate via network 120. A web-enabled device interface 131 can be used by the in-vehicle control system 150 to facilitate data communication between the in-vehicle control system 150 and the network 120 via the in-vehicle web-enabled device 130. Similarly, a user mobile device interface 133 can be used by the in-vehicle control system 150 to facilitate data communication between the in-vehicle control system 150 and the network 120 via the user mobile device 132. In this manner, the in-vehicle control system 150 can obtain real-time access to network resources 122 via network 120. The network resources 122 can be used to obtain processing modules for execution by data processor 171, data content to train internal neural networks, system parameters, or other data.

The ecosystem 101 can include a wide area data network 120. The network 120 represents one or more conventional wide area data networks, such as the Internet, a cellular telephone network, satellite network, pager network, a wireless broadcast network, gaming network, WiFi network, peer-to-peer network, Voice over IP (VoIP) network, etc. One or more of these networks 120 can be used to connect a user or client system with network resources 122, such as websites, servers, central control sites, or the like. The network resources 122 can generate and/or distribute data, which can be received in vehicle 105 via in-vehicle web-enabled devices 130 or user mobile devices 132. The network resources 122 can also host network cloud services, which can support the functionality used to compute or assist in processing object input or object input analysis. Antennas can serve to connect the in-vehicle control system 150 and the vehicle position and velocity estimation module 200 with the data network 120 via cellular, satellite, radio, or other conventional signal reception mechanisms. Such cellular data networks are currently available (e.g., Verizon™, AT&T™, T-Mobile™, etc.). Such satellite-based data or content networks are also currently available (e.g., SiriusXM™, HughesNet™, etc.). The conventional broadcast networks, such as AM/FM radio networks, pager networks, UHF networks, gaming networks, WiFi networks, peer-to-peer networks, Voice over IP (VoIP) networks, and the like are also well-known. Thus, as described in more detail below, the in-vehicle control system 150 and the vehicle position and velocity estimation module 200 can receive web-based data or content via an in-vehicle web-enabled device interface 131, which can be used to connect with the in-vehicle web-enabled device receiver 130 and network 120. In this manner, the in-vehicle control system 150 and the vehicle position and velocity estimation module 200 can support a variety of network-connectable in-vehicle devices and systems from within a vehicle 105.

As shown in FIG. 1 , the in-vehicle control system 150 and the vehicle position and velocity estimation module 200 can also receive data, object processing control parameters, and training content from user mobile devices 132, which can be located inside or proximately to the vehicle 105. The user mobile devices 132 can represent standard mobile devices, such as cellular phones, smartphones, personal digital assistants (PDA's), MP3 players, tablet computing devices (e.g., iPad™), laptop computers, CD players, and other mobile devices, which can produce, receive, and/or deliver data, object processing control parameters, and content for the in-vehicle control system 150 and the vehicle position and velocity estimation module 200. As shown in FIG. 1 , the mobile devices 132 can also be in data communication with the network cloud 120. The mobile devices 132 can source data and content from internal memory components of the mobile devices 132 themselves or from network resources 122 via network 120. Additionally, mobile devices 132 can themselves include a GPS data receiver, accelerometers, WiFi triangulation, or other geo-location sensors or components in the mobile device, which can be used to determine the real-time geo-location of the user (via the mobile device) at any moment in time. In any case, the in-vehicle control system 150 and the vehicle position and velocity estimation module 200 can receive data from the mobile devices 132 as shown in FIG. 1 .

Referring still to FIG. 1 , the example embodiment of ecosystem 101 can include vehicle operational subsystems 140. For embodiments that are implemented in a vehicle 105, many standard vehicles include operational subsystems, such as electronic control units (ECUs), supporting monitoring/control subsystems for the engine, brakes, transmission, electrical system, emissions system, interior environment, and the like. For example, data signals communicated from the vehicle operational subsystems 140 (e.g., ECUs of the vehicle 105) to the in-vehicle control system 150 via vehicle subsystem interface 141 may include information about the state of one or more of the components or subsystems of the vehicle 105. In particular, the data signals, which can be communicated from the vehicle operational subsystems 140 to a Controller Area Network (CAN) bus of the vehicle 105, can be received and processed by the in-vehicle control system 150 via vehicle subsystem interface 141. Embodiments of the systems and methods described herein can be used with substantially any mechanized system that uses a CAN bus or similar data communications bus as defined herein, including, but not limited to, industrial equipment, boats, trucks, machinery, or automobiles; thus, the term “vehicle” as used herein can include any such mechanized systems. Embodiments of the systems and methods described herein can also be used with any systems employing some form of network data communications; however, such network communications are not required.

Referring still to FIG. 1 , the example embodiment of ecosystem 101, and the vehicle operational subsystems 140 therein, can include a variety of vehicle subsystems in support of the operation of vehicle 105. In general, the vehicle 105 may take the form of a car, truck, motorcycle, bus, boat, airplane, helicopter, lawn mower, earth mover, snowmobile, aircraft, recreational vehicle, amusement park vehicle, farm equipment, construction equipment, tram, golf cart, train, and trolley, for example. Other vehicles are possible as well. The vehicle 105 may be configured to operate fully or partially in an autonomous mode. For example, the vehicle 105 may control itself while in the autonomous mode, and may be operable to determine a current state of the vehicle and its environment, determine a predicted behavior of at least one other vehicle in the environment, determine a confidence level that may correspond to a likelihood of the at least one other vehicle to perform the predicted behavior, and control the vehicle 105 based on the determined information. While in autonomous mode, the vehicle 105 may be configured to operate without human interaction.

The vehicle 105 may include various vehicle subsystems such as a vehicle drive subsystem 142, vehicle sensor subsystem 144, vehicle control subsystem 146, and occupant interface subsystem 148. As described above, the vehicle 105 may also include the in-vehicle control system 150, the computing system 170, and the vehicle position and velocity estimation module 200. The vehicle 105 may include more or fewer subsystems and each subsystem could include multiple elements. Further, each of the subsystems and elements of vehicle 105 could be interconnected. Thus, one or more of the described functions of the vehicle 105 may be divided up into additional functional or physical components or combined into fewer functional or physical components. In some further examples, additional functional and physical components may be added to the examples illustrated by FIG. 1 .

The vehicle drive subsystem 142 may include components operable to provide powered motion for the vehicle 105. In an example embodiment, the vehicle drive subsystem 142 may include an engine or motor, wheels/tires, a transmission, an electrical subsystem, and a power source. The engine or motor may be any combination of an internal combustion engine, an electric motor, steam engine, fuel cell engine, propane engine, or other types of engines or motors. In some example embodiments, the engine may be configured to convert a power source into mechanical energy. In some example embodiments, the vehicle drive subsystem 142 may include multiple types of engines or motors. For instance, a gas-electric hybrid car could include a gasoline engine and an electric motor. Other examples are possible.

The wheels of the vehicle 105 may be standard tires. The wheels of the vehicle 105 may be configured in various formats, including a unicycle, bicycle, tricycle, or a four-wheel format, such as on a car or a truck, for example. Other wheel geometries are possible, such as those including six or more wheels. Any combination of the wheels of vehicle 105 may be operable to rotate differentially with respect to other wheels. The wheels may represent at least one wheel that is fixedly attached to the transmission and at least one tire coupled to a rim of the wheel that could make contact with the driving surface. The wheels may include a combination of metal and rubber, or another combination of materials. The transmission may include elements that are operable to transmit mechanical power from the engine to the wheels. For this purpose, the transmission could include a gearbox, a clutch, a differential, and drive shafts. The transmission may include other elements as well. The drive shafts may include one or more axles that could be coupled to one or more wheels. The electrical system may include elements that are operable to transfer and control electrical signals in the vehicle 105. These electrical signals can be used to activate lights, servos, electrical motors, and other electrically driven or controlled devices of the vehicle 105. The power source may represent a source of energy that may, in full or in part, power the engine or motor. That is, the engine or motor could be configured to convert the power source into mechanical energy. Examples of power sources include gasoline, diesel, other petroleum-based fuels, propane, other compressed gas-based fuels, ethanol, fuel cell, solar panels, batteries, and other sources of electrical power. The power source could additionally or alternatively include any combination of fuel tanks, batteries, capacitors, or flywheels. The power source may also provide energy for other subsystems of the vehicle 105.

The vehicle sensor subsystem 144 may include a number of sensors configured to sense information about an environment or condition of the vehicle 105. For example, the vehicle sensor subsystem 144 may include an inertial measurement unit (IMU), a Global Positioning System (GPS) transceiver, a RADAR unit, a laser range finder/LIDAR unit, and one or more cameras or image capture devices. The vehicle sensor subsystem 144 may also include sensors configured to monitor internal systems of the vehicle 105 (e.g., an O2 monitor, a fuel gauge, an engine oil temperature). Other sensors are possible as well. One or more of the sensors included in the vehicle sensor subsystem 144 may be configured to be actuated separately or collectively in order to modify a position, an orientation, or both, of the one or more sensors.

The IMU may include any combination of sensors (e.g., accelerometers and gyroscopes) configured to sense position and orientation changes of the vehicle 105 based on inertial acceleration. The GPS transceiver may be any sensor configured to estimate a geographic location of the vehicle 105. For this purpose, the GPS transceiver may include a receiver/transmitter operable to provide information regarding the position of the vehicle 105 with respect to the Earth. The RADAR unit may represent a system that utilizes radio signals to sense objects within the local environment of the vehicle 105. In some embodiments, in addition to sensing the objects, the RADAR unit may additionally be configured to sense the speed and the heading of the objects proximate to the vehicle 105. The laser range finder or LIDAR unit may be any sensor configured to sense objects in the environment in which the vehicle 105 is located using lasers or other distance measuring equipment. In an example embodiment, the laser range finder/LIDAR unit may include one or more laser sources, a laser scanner, and one or more detectors, among other system components. The laser range finder/LIDAR unit could be configured to operate in a coherent (e.g., using heterodyne detection) or an incoherent detection mode. The cameras may include one or more devices configured to capture a plurality of images of the environment of the vehicle 105. The cameras may be still image cameras or motion video cameras.

The vehicle control system 146 may be configured to control operation of the vehicle 105 and its components. Accordingly, the vehicle control system 146 may include various elements such as a steering unit, a throttle, a brake unit, a navigation unit, and an autonomous control unit.

The steering unit may represent any combination of mechanisms that may be operable to adjust the heading of vehicle 105. The throttle may be configured to control, for instance, the operating speed of the engine and, in turn, control the speed of the vehicle 105. The brake unit can include any combination of mechanisms configured to decelerate the vehicle 105. The brake unit can use friction to slow the wheels in a standard manner. In other embodiments, the brake unit may convert the kinetic energy of the wheels to electric current. The brake unit may take other forms as well. The navigation unit may be any system configured to determine a driving path or route for the vehicle 105. The navigation unit may additionally be configured to update the driving path dynamically while the vehicle 105 is in operation. In some embodiments, the navigation unit may be configured to incorporate data from the vehicle position and velocity estimation module 200, the GPS transceiver, and one or more predetermined maps so as to determine the driving path for the vehicle 105. The autonomous control unit may represent a control system configured to identify, evaluate, and avoid or otherwise negotiate potential obstacles in the environment of the vehicle 105. In general, the autonomous control unit may be configured to control the vehicle 105 for operation without a driver or to provide driver assistance in controlling the vehicle 105. In some embodiments, the autonomous control unit may be configured to incorporate data from the vehicle position and velocity estimation module 200, the GPS transceiver, the RADAR, the LIDAR, the cameras, and other vehicle subsystems to determine the driving path or trajectory for the vehicle 105. The vehicle control system 146 may additionally or alternatively include components other than those shown and described.

Occupant interface subsystems 148 may be configured to allow interaction between the vehicle 105 and external sensors, other vehicles, other computer systems, and/or an occupant or user of vehicle 105. For example, the occupant interface subsystems 148 may include standard visual display devices (e.g., plasma displays, liquid crystal displays (LCDs), touchscreen displays, heads-up displays, or the like), speakers or other audio output devices, microphones or other audio input devices, navigation interfaces, and interfaces for controlling the internal environment (e.g., temperature, fan, etc.) of the vehicle 105.

In an example embodiment, the occupant interface subsystems 148 may provide, for instance, means for a user/occupant of the vehicle 105 to interact with the other vehicle subsystems. The visual display devices may provide information to a user of the vehicle 105. The user interface devices can also be operable to accept input from the user via a touchscreen. The touchscreen may be configured to sense at least one of a position and a movement of a user's finger via capacitive sensing, resistance sensing, or a surface acoustic wave process, among other possibilities. The touchscreen may be capable of sensing finger movement in a direction parallel or planar to the touchscreen surface, in a direction normal to the touchscreen surface, or both, and may also be capable of sensing a level of pressure applied to the touchscreen surface. The touchscreen may be formed of one or more translucent or transparent insulating layers and one or more translucent or transparent conducting layers. The touchscreen may take other forms as well.

In other instances, the occupant interface subsystems 148 may provide means for the vehicle 105 to communicate with devices within its environment. The microphone may be configured to receive audio (e.g., a voice command or other audio input) from a user of the vehicle 105. Similarly, the speakers may be configured to output audio to a user of the vehicle 105. In one example embodiment, the occupant interface subsystems 148 may be configured to wirelessly communicate with one or more devices directly or via a communication network. For example, a wireless communication system could use 3G cellular communication, such as CDMA, EVDO, GSM/GPRS, or 4G cellular communication, such as WiMAX or LTE. Alternatively, the wireless communication system may communicate with a wireless local area network (WLAN), for example, using WIFI®. In some embodiments, the wireless communication system 146 may communicate directly with a device, for example, using an infrared link, BLUETOOTH®, or ZIGBEE®. Other wireless protocols, such as various vehicular communication systems, are possible within the context of the disclosure. For example, the wireless communication system may include one or more dedicated short range communications (DSRC) devices that may include public or private data communications between vehicles and/or roadside stations.

Many or all of the functions of the vehicle 105 can be controlled by the computing system 170. The computing system 170 may include at least one data processor 171 (which can include at least one microprocessor) that executes processing instructions stored in a non-transitory computer readable medium, such as the data storage device 172. The computing system 170 may also represent a plurality of computing devices that may serve to control individual components or subsystems of the vehicle 105 in a distributed fashion. In some embodiments, the data storage device 172 may contain processing instructions (e.g., program logic) executable by the data processor 171 to perform various functions of the vehicle 105, including those described herein in connection with the drawings. The data storage device 172 may contain additional instructions as well, including instructions to transmit data to, receive data from, interact with, or control one or more of the vehicle drive subsystem 140, the vehicle sensor subsystem 144, the vehicle control subsystem 146, and the occupant interface subsystems 148.

In addition to the processing instructions, the data storage device 172 may store data such as object processing parameters, training data, roadway maps, and path information, among other information. Such information may be used by the vehicle 105 and the computing system 170 during the operation of the vehicle 105 in the autonomous, semi-autonomous, and/or manual modes.

The vehicle 105 may include a user interface for providing information to or receiving input from a user or occupant of the vehicle 105. The user interface may control or enable control of the content and the layout of interactive images that may be displayed on a display device. Further, the user interface may include one or more input/output devices within the set of occupant interface subsystems 148, such as the display device, the speakers, the microphones, or a wireless communication system.

The computing system 170 may control the function of the vehicle 105 based on inputs received from various vehicle subsystems (e.g., the vehicle drive subsystem 140, the vehicle sensor subsystem 144, and the vehicle control subsystem 146), as well as from the occupant interface subsystem 148. For example, the computing system 170 may use input from the vehicle control system 146 in order to control the steering unit to avoid an obstacle detected by the vehicle sensor subsystem 144 and follow a path or trajectory generated with the assistance of data from the vehicle position and velocity estimation module 200. In an example embodiment, the computing system 170 can be operable to provide control over many aspects of the vehicle 105 and its subsystems.

Although FIG. 1 shows various components of vehicle 105, e.g., vehicle subsystems 140, computing system 170, data storage device 172, and vehicle position and velocity estimation module 200, as being integrated into the vehicle 105, one or more of these components could be mounted or associated separately from the vehicle 105. For example, data storage device 172 could, in part or in full, exist separate from the vehicle 105. Thus, the vehicle 105 could be provided in the form of device elements that may be located separately or together. The device elements that make up vehicle 105 could be communicatively coupled together in a wired or wireless fashion.

Additionally, other data and/or content (denoted herein as ancillary data) can be obtained from local and/or remote sources by the in-vehicle control system 150 as described above. The ancillary data can be used to augment, modify, or train the operation of the vehicle position and velocity estimation module 200 based on a variety of factors including, the context in which the user is operating the vehicle (e.g., the location of the vehicle, the specified destination, direction of travel, speed, the time of day, the status of the vehicle, etc.), and a variety of other data obtainable from the variety of sources, local and remote, as described herein.

In a particular embodiment, the in-vehicle control system 150 and the vehicle position and velocity estimation module 200 can be implemented as in-vehicle components of vehicle 105. In various example embodiments, the in-vehicle control system 150 and the vehicle position and velocity estimation module 200 in data communication therewith can be implemented as integrated components or as separate components. In an example embodiment, the software components of the in-vehicle control system 150 and/or the vehicle position and velocity estimation module 200 can be dynamically upgraded, modified, and/or augmented by use of the data connection with the mobile devices 132 and/or the network resources 122 via network 120. The in-vehicle control system 150 can periodically query a mobile device 132 or a network resource 122 for updates or updates can be pushed to the in-vehicle control system 150.

Referring now to FIG. 2 , a diagram illustrates the components of the vehicle position and velocity estimation module 200 of an example embodiment. In the example embodiment, the vehicle position and velocity estimation module 200 can be configured to include a data collection module 173 and an inference and tracking module 175. As described in more detail below, the data collection module 173 and the inference and tracking module 175 serve to enable generation of an estimated position and velocity of proximate vehicles or objects relative to vehicle 105 based on input object data 210 received from one or more of the vehicle sensor subsystems 144, including one or more cameras and one or more LIDAR sensors. The input object data 210 can include image data from a camera, which can be processed by an image processing module to identify proximate objects (e.g., moving vehicles, dynamic agents, or other objects in the proximate vicinity of the vehicle 105). The input object data 210 can also include object distance data or point clouds from a LIDAR sensor, which can be processed by a LIDAR data processing module to determine a distance of each proximate object relative to the vehicle 105. The data collection module 173 and the inference and tracking module 175 can be configured as software modules executed by the data processor 171 of the in-vehicle control system 150. The modules 173 and 175 of the vehicle position and velocity estimation module 200 can receive the input object data 210 and produce proximate object position and velocity data 220, based on the generation of a 3D location and velocity of each proximate object from the input object data 210. The proximate object position and velocity data 220 can be used by the autonomous control subsystem of the vehicle control subsystem 146 to more efficiently and safely control the vehicle 105. As part of the generation of the proximate object position and velocity data 220, the data collection module 173 and the inference and tracking module 175 can be configured to work with inference and tracking configuration parameters 174, which can be used to customize and fine tune the operation of the vehicle position and velocity estimation module 200. The inference and tracking configuration parameters 174 can be stored in a memory 172 of the in-vehicle control system 150.

In the example embodiment, the vehicle position and velocity estimation module 200 can be configured to include an interface with the in-vehicle control system 150, as shown in FIG. 1 , through which the vehicle position and velocity estimation module 200 can send and receive data as described herein. Additionally, the vehicle position and velocity estimation module 200 can be configured to include an interface with the in-vehicle control system 150 and/or other ecosystem 101 subsystems through which the vehicle position and velocity estimation module 200 can receive ancillary data from the various data sources described above. As described above, the vehicle position and velocity estimation module 200 can also be implemented in systems and platforms that are not deployed in a vehicle and not necessarily used in or with a vehicle.

In an example embodiment as shown in FIG. 2 , the vehicle position and velocity estimation module 200 can be configured to include the data collection module 173 and the inference and tracking module 175, as well as other processing modules not shown for clarity. Each of these modules can be implemented as software, firmware, or other logic components executing or activated within an executable environment of the vehicle position and velocity estimation module 200 operating within or in data communication with the in-vehicle control system 150. Each of these modules of an example embodiment is described in more detail below in connection with the figures provided herein.

Proximate Vehicle Position and Velocity Estimation Based on Camera and LIDAR Data

A system and method for vehicle position and velocity estimation based on camera and LIDAR data is disclosed herein. Specifically, the example embodiments described herein relate to a system and method to detect and estimate the position of proximate vehicles or other objects in the vicinity of an autonomous vehicle. The example embodiment can also estimate the velocity of the proximate vehicles or objects relative to the autonomous vehicle. The example embodiment can also generate velocity vectors corresponding to the proximate vehicles or objects. The system and method of an example embodiment can include two components or phases: 1) a data collection component/phase, and 2) an inference and tracking component/phase. In the data collection phase, a vehicle, on which is mounted one or more cameras and one or more LIDAR sensors, collects multiple frames of images from the camera(s) and multiple LIDAR point clouds, respectively, at a pre-determined time or cycle interval (e.g., 50 milliseconds). In the inference and tracking component/phase, implemented in an example embodiment by an inference and tracking module, two-dimensional (2D) positions of proximate vehicles and other objects can be detected using the image data from the camera(s). Additionally, distance data, corresponding to the objects detected from the image data, can be obtained from the LIDAR point clouds. Using both the 2D positions of proximate vehicles determined from the image data and the estimates of relative distance of the proximate vehicles or objects using the LIDAR distance data, the inference and tracking module can determine the precise relative three dimensional (3D) position of proximate vehicles relative to the autonomous vehicle. As multiple estimates of position are determined over time at a pre-determined sample rate or cycle time (e.g., 50 milliseconds), the inference and tracking module may also determine the estimated relative velocity and velocity vector of each proximate vehicle relative to the autonomous vehicle. With the assistance of a 3D tracking process, the system of an example embodiment can determine the relative 3D positions and velocities of proximate vehicles using camera image data and LIDAR distance data, even when intermittent, errant, or unstable, camera image data and/or LIDAR data is received.

FIG. 3 illustrates the components of the vehicle position and velocity estimation module 200 of an example embodiment. As shown, the vehicle position and velocity estimation module 200 can be configured to include a data collection module 173 and an inference and tracking module 175. The vehicle position and velocity estimation module 200, and the data collection module 173 therein, can receive input object data 210 from one or more of the vehicle sensor subsystems 144, including one or more cameras and one or more LIDAR sensors. The input object data 210 can include image data 212 from a video stream generated by an image generating device, such as a camera. The input object data 210 can also include distance data 213 from a distance measuring device, such as a LIDAR sensor device. The image data 212 from the input object data 210 can be processed by an image data processing module 214 to identify proximate vehicles or other objects (e.g., moving vehicles, dynamic agents, or other objects in the proximate vicinity of the vehicle 105). For example, a process of semantic segmentation and/or object detection can be used to process the image data and identify objects in the images. The objects identified in the input image data can be designated by bounding boxes or other information useful for extracting object data from the image data. The object data extracted from the image data can be used to determine a two-dimensional (2D) position of the object. The 2D position of the object can be used to determine if the object is within a pre-determined distance from the current position of the autonomous vehicle 105 and thus, a proximate object. The 2D position of proximate objects identified in the image data can be provided as an input to a matching and inference processing module 218 described in more detail below.

Referring still to FIG. 3 , the input object data 210 includes distance data 213 from the distance measuring device, such as a LIDAR sensor device. The distance data 213 can be represented as point clouds from the LIDAR. The distance data 213 from the input object data 210 can be processed by a LIDAR distance data processing module 215. The LIDAR distance data processing module 215 can use the input distance data 213 or LIDAR point clouds to identify potential objects (e.g., moving vehicles, dynamic agents, or other objects in the vicinity of the vehicle 105) proximate to the vehicle 105. The distance data 213 also enables the LIDAR distance data processing module 215 to measure the distances from the vehicle 105 to each of the potential proximate objects with a high degree of precision. The data related to the identified objects and corresponding distance measurements generated by the LIDAR distance data processing module 215 can be output to both an object tracking module 217 and the matching and inference processing module 218.

The object tracking module 217 is responsible for tracking the identified objects across a plurality of processing cycles or iterations of the collection of the distance data 213. The object tracking module 217 is configured to correlate the positions and velocities of the identified objects 211 found in a previous processing cycle with the objects identified in the current processing cycle. In this manner, the movement and changes in the distance measurement for a particular object can be correlated across multiple cycles. An object missing from the current distance data 213 can still be checked for presence in a subsequent cycle in case the current distance data 213 is incomplete, errant, or otherwise compromised. In this manner, the object tracking module 217 can track identified objects even when the input object data 210 is intermittent, errant, or unstable. Once the vehicle position and velocity estimation module 200 generates the positions and velocities of proximate objects 220 for a current cycle, the positions and velocities of the proximate objects can be saved as the position and velocity data from a previous cycle 211 and used for a subsequent processing cycle. The data related to the identified and tracked objects and their corresponding distance measurements can be output by the object tracking module 217 and provided as an input to the matching and inference processing module 218.

The matching and inference processing module 218 is responsible for correlating the objects identified from the image (camera) data 212 with the objects identified and tracked from the distance (LIDAR) data 213. Given the 2D position of proximate objects identified by the image data processing module 214 and the distance measurements of the identified and tracked objects provided by the LIDAR distance data processing module 215 and the object tracking module 217, the matching and inference processing module 218 can match the positions of objects detected in the image data with objects detected in the LIDAR data. As a result, the 2D positions of the detected objects can be matched with the corresponding distances of the detected objects, which can render the position of each detected object in three-dimensional (3D) space. Thus, the matching and inference processing module 218 can determine a three-dimensional (3D) position of each proximate object using a combination of the image data from the image generating device and the distance data from the distance measuring device. Additionally, the three-dimensional (3D) position of each proximate object can be generated and tracked over a plurality of processing cycles. Newly identified objects that do not appear in the tracking data and hence do not correlate to any object in any previous cycle can be designated as a new object and the tracking of the new object can be initiated. The matching and inference processing module 218 can use the 3D positions and tracking data over multiple cycles to determine a velocity of each proximate object. Therefore, the matching and inference processing module 218 can determine a velocity and velocity vector for each of the detected proximate objects. The data corresponding to the 3D positions and velocities of each proximate object can be provided as an output of the matching and inference processing module 218 and the vehicle position and velocity estimation module 200 described herein.

Other subsystems of vehicle 105, as described above, can use the 3D positions and velocities of each proximate object to perform a variety of additional processing functions. For example, the 3D positions and velocities of each proximate object can be used by a trajectory planning module to generate a path for the vehicle 105 that does not intersect or interfere with the paths of the proximate objects. Additionally, the 3D positions and velocities of each proximate object can be used by a planning module to anticipate or infer future actions based on the behavior of proximate objects. The future actions could include generating control signals to modify the operation of the vehicle 105, the generation of alerts to a driver of the vehicle 105, or other actions relative to the operation of the vehicle 105

Referring now to FIG. 4 , a flow diagram illustrates an example embodiment of a system and method 1000 for vehicle position and velocity estimation based on camera and LIDAR data. The example embodiment can be configured for: receiving input object data from a subsystem of an autonomous vehicle, the input object data including image data from an image generating device and distance data from a distance measuring device (processing block 1010); determining a two-dimensional (2D) position of a proximate object near the autonomous vehicle using the image data received from the image generating device (processing block 1020); tracking a three-dimensional (3D) position of the proximate object using the distance data received from the distance measuring device over a plurality of cycles and generating tracking data (processing block 1030); determining a 3D position of the proximate object using the 2D position, the distance data received from the distance measuring device, and the tracking data (processing block 1040); determining a velocity of the proximate object using the 3D position and the tracking data (processing block 1050); and outputting the 3D position and velocity of the proximate object relative to the autonomous vehicle (processing block 1060).

As used herein and unless specified otherwise, the term “mobile device” includes any computing or communications device that can communicate with the in-vehicle control system 150 and/or the vehicle position and velocity estimation module 200 described herein to obtain read or write access to data signals, messages, or content communicated via any mode of data communications. In many cases, the mobile device 130 is a handheld, portable device, such as a smart phone, mobile phone, cellular telephone, tablet computer, laptop computer, display pager, radio frequency (RF) device, infrared (IR) device, global positioning device (GPS), Personal Digital Assistants (PDA), handheld computers, wearable computer, portable game console, other mobile communication and/or computing device, or an integrated device combining one or more of the preceding devices, and the like. Additionally, the mobile device 130 can be a computing device, personal computer (PC), multiprocessor system, microprocessor-based or programmable consumer electronic device, network PC, diagnostics equipment, a system operated by a vehicle 105 manufacturer or service technician, and the like, and is not limited to portable devices. The mobile device 130 can receive and process data in any of a variety of data formats. The data format may include or be configured to operate with any programming format, protocol, or language including, but not limited to, JavaScript, C++, iOS, Android, etc.

As used herein and unless specified otherwise, the term “network resource” includes any device, system, or service that can communicate with the in-vehicle control system 150 and/or the vehicle position and velocity estimation module 200 described herein to obtain read or write access to data signals, messages, or content communicated via any mode of inter-process or networked data communications. In many cases, the network resource 122 is a data network accessible computing platform, including client or server computers, websites, mobile devices, peer-to-peer (P2P) network nodes, and the like. Additionally, the network resource 122 can be a web appliance, a network router, switch, bridge, gateway, diagnostics equipment, a system operated by a vehicle 105 manufacturer or service technician, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term “machine” can also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein. The network resources 122 may include any of a variety of providers or processors of network transportable digital content. Typically, the file format that is employed is Extensible Markup Language (XML), however, the various embodiments are not so limited, and other file formats may be used. For example, data formats other than Hypertext Markup Language (HTML)/XML or formats other than open/standard data formats can be supported by various embodiments. Any electronic file format, such as Portable Document Format (PDF), audio (e.g., Motion Picture Experts Group Audio Layer 3-MP3, and the like), video (e.g., MP4, and the like), and any proprietary interchange format defined by specific content sites can be supported by the various embodiments described herein.

The wide area data network 120 (also denoted the network cloud) used with the network resources 122 can be configured to couple one computing or communication device with another computing or communication device. The network may be enabled to employ any form of computer readable data or media for communicating information from one electronic device to another. The network 120 can include the Internet in addition to other wide area networks (WANs), cellular telephone networks, metro-area networks, local area networks (LANs), other packet-switched networks, circuit-switched networks, direct data connections, such as through a universal serial bus (USB) or Ethernet port, other forms of computer-readable media, or any combination thereof. The network 120 can include the Internet in addition to other wide area networks (WANs), cellular telephone networks, satellite networks, over-the-air broadcast networks, AM/FM radio networks, pager networks, UHF networks, other broadcast networks, gaming networks, WiFi networks, peer-to-peer networks, Voice Over IP (VoIP) networks, metro-area networks, local area networks (LANs), other packet-switched networks, circuit-switched networks, direct data connections, such as through a universal serial bus (USB) or Ethernet port, other forms of computer-readable media, or any combination thereof. On an interconnected set of networks, including those based on differing architectures and protocols, a router or gateway can act as a link between networks, enabling messages to be sent between computing devices on different networks. Also, communication links within networks can typically include twisted wire pair cabling, USB, Firewire, Ethernet, or coaxial cable, while communication links between networks may utilize analog or digital telephone lines, full or fractional dedicated digital lines including T1, T2, T3, and T4, Integrated Services Digital Networks (ISDNs), Digital User Lines (DSLs), wireless links including satellite links, cellular telephone links, or other communication links known to those of ordinary skill in the art. Furthermore, remote computers and other related electronic devices can be remotely connected to the network via a modem and temporary telephone link.

The network 120 may further include any of a variety of wireless sub-networks that may further overlay stand-alone ad-hoc networks, and the like, to provide an infrastructure-oriented connection. Such sub-networks may include mesh networks, Wireless LAN (WLAN) networks, cellular networks, and the like. The network may also include an autonomous system of terminals, gateways, routers, and the like connected by wireless radio links or wireless transceivers. These connectors may be configured to move freely and randomly and organize themselves arbitrarily, such that the topology of the network may change rapidly. The network 120 may further employ one or more of a plurality of standard wireless and/or cellular protocols or access technologies including those set forth herein in connection with network interface 712 and network 714 described in the figures herewith.

In a particular embodiment, a mobile device 132 and/or a network resource 122 may act as a client device enabling a user to access and use the in-vehicle control system 150 and/or the vehicle position and velocity estimation module 200 to interact with one or more components of a vehicle subsystem. These client devices 132 or 122 may include virtually any computing device that is configured to send and receive information over a network, such as network 120 as described herein. Such client devices may include mobile devices, such as cellular telephones, smart phones, tablet computers, display pagers, radio frequency (RF) devices, infrared (IR) devices, global positioning devices (GPS), Personal Digital Assistants (PDAs), handheld computers, wearable computers, game consoles, integrated devices combining one or more of the preceding devices, and the like. The client devices may also include other computing devices, such as personal computers (PCs), multiprocessor systems, microprocessor-based or programmable consumer electronics, network PC's, and the like. As such, client devices may range widely in terms of capabilities and features. For example, a client device configured as a cell phone may have a numeric keypad and a few lines of monochrome LCD display on which only text may be displayed. In another example, a web-enabled client device may have a touch sensitive screen, a stylus, and a color LCD display screen in which both text and graphics may be displayed. Moreover, the web-enabled client device may include a browser application enabled to receive and to send wireless application protocol messages (WAP), and/or wired application messages, and the like. In one embodiment, the browser application is enabled to employ HyperText Markup Language (HTML), Dynamic HTML, Handheld Device Markup Language (HDML), Wireless Markup Language (WML), WMLScript, JavaScript™, EXtensible HTML (xHTML), Compact HTML (CHTML), and the like, to display and send a message with relevant information.

The client devices may also include at least one client application that is configured to receive content or messages from another computing device via a network transmission. The client application may include a capability to provide and receive textual content, graphical content, video content, audio content, alerts, messages, notifications, and the like. Moreover, the client devices may be further configured to communicate and/or receive a message, such as through a Short Message Service (SMS), direct messaging (e.g., Twitter), email, Multimedia Message Service (MMS), instant messaging (IM), internet relay chat (IRC), mIRC, Jabber, Enhanced Messaging Service (EMS), text messaging, Smart Messaging, Over the Air (OTA) messaging, or the like, between another computing device, and the like. The client devices may also include a wireless application device on which a client application is configured to enable a user of the device to send and receive information to/from network resources wirelessly via the network.

The in-vehicle control system 150 and/or the vehicle position and velocity estimation module 200 can be implemented using systems that enhance the security of the execution environment, thereby improving security and reducing the possibility that the in-vehicle control system 150 and/or the vehicle position and velocity estimation module 200 and the related services could be compromised by viruses or malware. For example, the in-vehicle control system 150 and/or the vehicle position and velocity estimation module 200 can be implemented using a Trusted Execution Environment, which can ensure that sensitive data is stored, processed, and communicated in a secure way.

FIG. 5 shows a diagrammatic representation of a machine in the example form of a computing system 700 within which a set of instructions when executed and/or processing logic when activated may cause the machine to perform any one or more of the methodologies described and/or claimed herein. In alternative embodiments, the machine operates as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine may operate in the capacity of a server or a client machine in server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine may be a personal computer (PC), a laptop computer, a tablet computing system, a Personal Digital Assistant (PDA), a cellular telephone, a smartphone, a web appliance, a set-top box (STB), a network router, switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) or activating processing logic that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term “machine” can also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions or processing logic to perform any one or more of the methodologies described and/or claimed herein.

The example computing system 700 can include a data processor 702 (e.g., a System-on-a-Chip (SoC), general processing core, graphics core, and optionally other processing logic) and a memory 704, which can communicate with each other via a bus or other data transfer system 706. The mobile computing and/or communication system 700 may further include various input/output (I/O) devices and/or interfaces 710, such as a touchscreen display, an audio jack, a voice interface, and optionally a network interface 712. In an example embodiment, the network interface 712 can include one or more radio transceivers configured for compatibility with any one or more standard wireless and/or cellular protocols or access technologies (e.g., 2nd (2G), 2.5, 3rd (3G), 4th (4G) generation, and future generation radio access for cellular systems, Global System for Mobile communication (GSM), General Packet Radio Services (GPRS), Enhanced Data GSM Environment (EDGE), Wideband Code Division Multiple Access (WCDMA), LTE, CDMA2000, WLAN, Wireless Router (WR) mesh, and the like). Network interface 712 may also be configured for use with various other wired and/or wireless communication protocols, including TCP/IP, UDP, SIP, SMS, RTP, WAP, CDMA, TDMA, UMTS, UWB, WiFi, WiMax, Bluetooth™, IEEE 802.11x, and the like. In essence, network interface 712 may include or support virtually any wired and/or wireless communication and data processing mechanisms by which information/data may travel between a computing system 700 and another computing or communication system via network 714.

The memory 704 can represent a machine-readable medium on which is stored one or more sets of instructions, software, firmware, or other processing logic (e.g., logic 708) embodying any one or more of the methodologies or functions described and/or claimed herein. The logic 708, or a portion thereof, may also reside, completely or at least partially within the processor 702 during execution thereof by the mobile computing and/or communication system 700. As such, the memory 704 and the processor 702 may also constitute machine-readable media. The logic 708, or a portion thereof, may also be configured as processing logic or logic, at least a portion of which is partially implemented in hardware. The logic 708, or a portion thereof, may further be transmitted or received over a network 714 via the network interface 712. While the machine-readable medium of an example embodiment can be a single medium, the term “machine-readable medium” should be taken to include a single non-transitory medium or multiple non-transitory media (e.g., a centralized or distributed database, and/or associated caches and computing systems) that store the one or more sets of instructions. The term “machine-readable medium” can also be taken to include any non-transitory medium that is capable of storing, encoding or carrying a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the various embodiments, or that is capable of storing, encoding or carrying data structures utilized by or associated with such a set of instructions. The term “machine-readable medium” can accordingly be taken to include, but not be limited to, solid-state memories, optical media, and magnetic media.

The Abstract of the Disclosure is provided to allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment. 

What is claimed is:
 1. A system comprising: a data processor; and a vehicle position and velocity estimation module which, when executed by the data processor, causes the system to: receive input object data from a subsystem of vehicle, the input object data including image data from an image generating device and distance data from a distance measuring device, the distance measuring device comprising one or more light imaging, detection, and ranging (LIDAR) sensors; determine a first position of a proximate object near the vehicle from the image data; determine a second position of the proximate object from the distance data, the second position being tracked using the distance data received from the distance measuring device over a plurality of processing cycles, the distance data being collected during at least one of the plurality of processing cycles; correlate the first position and the second position by matching the first position of the proximate object detected in the image data with the second position of the same proximate object detected in the distance data; determine a three-dimensional (3D) position of the proximate object using the correlated first and second positions; and use the 3D position of the proximate object to navigate the vehicle.
 2. The system of claim 1 wherein the image generating device is one or more cameras and the second position is a 3D position.
 3. The system of claim 1 being further configured to determine the first position as a two-dimensional (2D) position of the proximate object using the image data received from the image generating device.
 4. The system of claim 1 being further configured to determine the 3D position of the proximate object using a two-dimensional (2D) position and a point cloud of the distance data received from the distance measuring device.
 5. The system of claim 1 being further configured to retain the 3D position of the proximate object as tracking data over the plurality of processing cycles.
 6. The system of claim 5 being further configured to determine a velocity of the proximate object using the 3D position and the tracking data.
 7. The system of claim 1 wherein the vehicle is an autonomous vehicle.
 8. The system of claim 7 being further configured to output the 3D position of the proximate object to a trajectory planning module of the autonomous vehicle.
 9. A method comprising: receiving input object data from a subsystem of a vehicle, the input object data including image data from an image generating device and distance data from a distance measuring device, the distance measuring device comprising one or more light imaging, detection, and ranging (LIDAR) sensors; determining a first position of a proximate object near the vehicle from the image data; determining a second position of the proximate object from the distance data, the second position being tracked using the distance data received from the distance measuring device over a plurality of processing cycles, the distance data being collected during at least one of the plurality of processing cycles; correlating the first position and the second position by matching the first position of the proximate object detected in the image data with the second position of the same proximate object detected in the distance data; determining a three-dimensional (3D) position of the proximate object using the correlated first and second positions; and using the 3D position of the proximate object to navigate the vehicle.
 10. The method of claim 9 wherein the image generating device is one or more cameras.
 11. The method of claim 9 wherein the second position is a 3D position.
 12. The method of claim 9 including determining the first position as a two-dimensional (2D) position of the proximate object using the image data received from the image generating device, the image generating device being a plurality of cameras.
 13. The method of claim 9 including determining the 3D position of the proximate object using a two-dimensional (2D) position and a point cloud generated by one or more LIDAR sensors.
 14. The method of claim 9 including retaining the 3D position of the proximate object as tracking data over the plurality of processing cycles in a memory device of an in-vehicle control system.
 15. The method of claim 9 including tracking the 3D position of the proximate object and determining a velocity of the proximate object using the 3D position and the tracking data.
 16. The method of claim 9 including correlating positions and velocities of proximate objects found in a previous processing cycle with proximate objects identified in a current processing cycle.
 17. The method of claim 9 including generating an alert if the 3D position of the proximate object may intersect with a trajectory of the vehicle.
 18. A non-transitory machine-useable storage medium embodying instructions which, when executed by at least one processor, cause the at least one processor to: receive input object data from a subsystem of a vehicle, the input object data including image data from an image generating device and distance data from a distance measuring device, the distance measuring device comprising one or more light imaging, detection, and ranging (LIDAR) sensors; determine a first position of a proximate object near the vehicle from the image data; determine a second position of the proximate object from the distance data, the second position being tracked using the distance data received from the distance measuring device over a plurality of processing cycles, the distance data being collected during at least one of the plurality of processing cycles; correlate the first position and the second position by matching the first position of the proximate object detected in the image data with the second position of the same proximate object detected in the distance data; determine a three-dimensional (3D) position of the proximate object using the correlated first and second positions; and use the 3D position of the proximate object to navigate the vehicle.
 19. The non-transitory machine-useable storage medium of claim 18 being further configured to correlate positions of proximate objects found in a previous processing cycle with proximate objects identified in a current processing cycle.
 20. The non-transitory machine-useable storage medium of claim 18 being further configured to determine a velocity of the proximate object using the 3D position and tracking data corresponding to the 3D position of the proximate object tracked over multiple processing cycles. 